Skip to content

FEAT: Generate datasets from a policy in the GUI (-6) - #4135

Open
Richard Lundeen (richlundeen) wants to merge 60 commits into
microsoft:mainfrom
richlundeen:richlundeen-assert-gui-generation-plan
Open

Richard Lundeen (richlundeen) wants to merge 60 commits into
microsoft:mainfrom
richlundeen:richlundeen-assert-gui-generation-plan

Conversation

@richlundeen

@richlundeen Richard Lundeen (richlundeen) commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Part -6 of the ASSERT stack. Design and how to use it: ASSERT in PyRIT.

PR
-1 #4132 Judge dimensions, presets and shared techniques merged
-2 #4130 Trace evidence (OpenTelemetry) merged
-3 #4131 Headline metrics merged
-4 #4133 Staged generation (SDK) merged
-5 #4134 Generation jobs (backend) merged
-5.5 #4476 Scanner dataset selection merged
-6 #4135 Generate from the GUI this PR
-7 #4144 In-process agents (docs)
-8 #4180 Scenario-aware dataset compatibility
-9 #4226 ASSERT results grouped by generated category
-10 #4228 Background dataset loading (all scanners)

The layers below this one are merged into main, so the Files changed tab shows only this PR's changes.

Description

In CoPyRIT, you can write a policy such as "Explain published return policies. Do not disclose another customer's private order details." or start from a bundled ASSERT behavior. You can then generate and optionally review an ASSERT dataset, and open foundry.assert_policy with it selected. The same pages also generate ordinary objective datasets, and every scanner that takes any named dataset links to generating datasets.

  • Datasets > Generate datasets opens the generator chooser:
    • The generations list groups suite members, with a cancel per member and a link to run the scenario on all of them once they finish.
    • The job page shows stage progress and offers cancel, retry, delete, and Edit & regenerate.
    • Each generator plugs in its own review step and result summary.
  • ASSERT form: bundled behavior and suite templates, coverage dimensions, and advanced sampling. Every target role starts with the default adversarial target, also when the target registry loads after the form. Pause-for-review is optional. A debounced server preflight reports validation errors, target problems (including web-search support), name availability and an estimate; a failed check can be run again. Suite mode creates one dataset per behavior in a single batch, and a problem every behavior shares is listed once.
  • Review editor: edit the taxonomy's categories (definition, examples, permissible, add or remove), terms, and dimension levels, then continue generation. If the review was continued or cancelled elsewhere, the page reloads the generation instead of failing on every click.
  • Edit & regenerate pre-fills a new form. For a reviewed ASSERT dataset it reuses the reviewed taxonomy unless you turn that off or change the policy, its context or the category count.
  • Objective datasets: a form for the target-objective generator. A generator the GUI doesn't know shows a frontend/backend version mismatch message.
  • Catalog and dataset pages: the catalog gains Generate datasets. Dataset pages for generated datasets gain Edit & regenerate.
  • Scanner launch pages:
    • Scanners that take any named dataset show Generate datasets next to Browse datasets in the Datasets header. Scanners with fixed or allow-listed datasets show only Browse datasets.
    • The scenario preset editor offers Generate datasets the same way, for the preset's scenario.
    • Completed ASSERT generations link to foundry.assert_policy with a ?dataset= link, so the generated dataset is preselected.
    • The scanner dataset changes that don't need generation (required datasets through ScenarioDatasetOptions.min_selected, choosing the first dataset, Browse datasets in the header, Reset datasets, ?dataset= links, the server's validation messages and the catalog's Origins filter) moved to FEAT: Scanner dataset selection: required, linked and first datasets (-5.5) #4476 (-5.5), which is merged into main.
  • An isolated Playwright journey runs over an offline generation target and is wired into CI. The GUI and scanner docs describe the flow.

Paste a policy, here the example above, and start an ASSERT generation:

ASSERT generation form with the example policy, a coverage dimension, target roles, pause for review and the estimate

Review the generated policy before seed groups are written:

Paused generation with the review editor for the generated taxonomy

The completed generation, with coverage, per-category counts, and the link to run foundry.assert_policy:

Completed ASSERT generation with summary tiles, the category table and Run foundry.assert_policy

foundry.assert_policy opened from the completed generation: the generated dataset is selected, and Generate datasets is new next to Browse datasets.

foundry.assert_policy opened from the completed generation with the generated dataset selected and Generate datasets next to Browse datasets

GUI behavior and scope

Own GUI changes (ASSERT-specific):

  • The ASSERT single-policy and suite forms, the taxonomy review step, and the ASSERT result summary.
  • Generate datasets on foundry.assert_policy opens the ASSERT form directly.

Shared / non-ASSERT impact. These are this PR's own changes, and users of other scanners and ordinary datasets see them:

  • Routes: /datasets/generate, /datasets/generate/new and /datasets/generate/:generationId, with a generator chooser but no new sidebar section.
  • Objective generation: the ordinary target-objective form, the generations list and the job pages, shared by both generators.
  • Catalog: Generate datasets (opens the generator chooser).
  • Dataset pages: Edit & regenerate appears for loaded named datasets a known generator made, including objective datasets. A failed lookup other than "not found" shows a retryable error instead of hiding the action.
  • Generate datasets on scanner launch pages and in the scenario preset editor appears next to Browse datasets only when the scanner accepts any named dataset. It opens the generator chooser unless exactly one generator follows up the scenario, and stays unavailable until the runtime's generator list loads.

From #4476 (-5.5), not this PR: Browse datasets in the Datasets header, Reset datasets, required datasets (ScenarioDatasetOptions.min_selected), choosing the first dataset, inline-only scenarios, linked ?dataset= names, the server's 422 field messages and the catalog's Origins facet. They were part of this PR until they moved to #4476, which is merged into main.

Unchanged / deferred:

Known limitations:

  • One backend owns generation records (see FEAT: Prompt generation jobs in the backend (-5) #4134). Several backends sharing one results storage aren't supported.
  • Concurrent review edits are last-write-wins. Review saves carry no version check, so if the same review is open in two tabs, the last successful save replaces the other tab's edits without a warning. The merged FEAT: Prompt generation jobs in the backend (-5) #4134 backend has no review version, so this PR doesn't restore that check.
  • The generations list doesn't poll paused rows. It refreshes when opened; the job page reloads on its own.
  • A failed generator-list refresh can lose unsaved form input. The form is replaced by an error page, and Retry remounts it from its original values.
  • Dataset uploads and generations reserve names separately (see FEAT: Prompt generation jobs in the backend (-5) #4134), so an upload can take a running generation's name and make its save fail.
Complete own-layer generation UI inventory

List/detail and actions (both generators). The list shows dataset, generator, status, progress, creation time, and actions; batch members are grouped in request order. States are Queued, Running, Review needed, Completed, Failed, Cancelled, and Interrupted. Active list and detail pages poll every two seconds; a failed refresh retries once, then shows an error or a stale-record warning with Check again. Records are scoped to the runtime and job ID and wait for runtime readiness. Detail shows stages, timestamps, creator and ID, persisted errors, and generator-specific results; if the generator list fails to load, it shows an error with Retry. Cancel has explicit errors and a detail-page confirmation. Failed, cancelled and interrupted jobs offer Retry from the last checkpoint. Edit & regenerate pre-fills a new form with a distinct _vN name. Inactive records can be deleted after a confirmation that says saved datasets are kept. Completed jobs offer Browse dataset and the declared Run scenario link; a completed batch can send all member datasets to one launch form.

Shared forms and targets. Changing the generator, source or template URL starts a fresh form. A request opened from an earlier generation keeps its targets; a request read from a dataset uses the configured defaults. Target roles follow the configured default adversarial target until the user chooses; explicit choices survive late registry or default updates. Required fields and limits appear before generation; target and capability problems come from the server preflight. Valid, settled inputs trigger a preflight after 500 ms for configuration, target and name checks and an estimate, without model calls. Estimates show call and token ranges, stages and exclusions; Check again retries a failed check, and a transport failure still lets you try Generate. While the generator list reloads after a runtime change, the form stays mounted but can't submit. A generator without a frontend form shows an explicit version-mismatch message.

ASSERT form. Single-policy and suite modes provide bundled behavior and suite templates, policy name and text, and application context. Output names follow the behavior or suite until edited; edited suite member names persist, and long suite labels are shortened so each behavior's name stays distinct. Controls include seed-group and category counts, user-prompt and adversarial-prompt inclusion, described or generated coverage dimensions or explicit levels, with add, remove and edit validation. Advanced controls include sampling method, random seed, stratification, factorial replication, replacement, web search, and default, custom or target-owned instructions. Defaults: 25 groups, 25 suggested categories, three generated levels, pairwise sampling, seed 0, web search off, user prompts on, adversarial prompts off. Generation and research target pickers and an optional pause after coverage-dimension resolution are available.

ASSERT review. Shows the research context and edits the behavior, categories, permissible flags, examples, terms and coverage levels. Examples you don't edit are sent back unchanged. Save persists edits; Continue saves pending edits before resuming. Reload, save and continue failures are explicit, and a 409 (the review moved on elsewhere) reloads the generation. Saving refreshes the estimate; a failed estimate shows the server's error with Check again. Saves are last-write-wins (see Known limitations).

Target-objective form (non-ASSERT). Shares the naming, target, estimate and submission machinery, with instructions, an objective count starting at 20 (1 to 1,000), and comma-separated harm labels. Name and generation target are required. There's no review pause because that generator has no reviewable stage; progress shows how many objectives were generated.

Screenshots: captured over a synthetic offline fixture, with no provider or model calls. The launch-page and catalog images were recaptured at 2342519 after merging #4476, and the preset editor image at 474deff. On launch pages and in the preset editor, only Generate datasets is from this PR.

More screenshots

Catalog (shared): Generate datasets in the header.

Dataset catalog with Generate datasets in the header

Generator chooser (shared):

Generator chooser listing the ASSERT and objective generators

ASSERT suite mode: one dataset per behavior from a bundled suite, with full-width name fields.

ASSERT suite mode from the telecom template with one dataset name per behavior

Generated dataset page (shared): Edit & regenerate.

Generated dataset page with Edit and regenerate

foundry.assert_policy at 390 px: Generate datasets stacks under Browse datasets in the Datasets header.

foundry.assert_policy Datasets section at 390 px with Browse datasets and Generate datasets

Ordinary scanner (shared): foundry.red_team_agent with Generate datasets next to Browse datasets.

foundry.red_team_agent Datasets section with Browse datasets and Generate datasets

Scenario preset editor (shared): a foundry.red_team_agent preset with Generate datasets next to Browse datasets below its dataset table.

Scenario preset editor Datasets section for foundry.red_team_agent with Browse datasets and Generate datasets below the dataset table

Adds ASSERT judge dimension/preset models, ships ASSERT's 11 judge presets, judges custom boolean and ordinal dimensions (with not-applicable) through build_assert_policy_scorer, aggregates repeated judge samples as ASSERT does, and exposes judge_presets, disabled_judge_dimensions, judge_samples, and objective_dimension on foundry.assert_policy. Default identities are unchanged.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ge presets to built-in names

- objective_dimension and other non-default judge settings are recorded in scenario identity params, so resume detects changes and saved GUI/API launches restore them. Default identities are unchanged.
- Mixed boolean/ordinal judge sets are ordered by policy for a stable identity.
- judge_presets accepts only shipped preset names; preset files move to the Python-only judge_preset_files (list[Path]) parameter, which the API guard rejects. Preset load errors no longer echo file contents.
- Adds a Scenario._get_identity_params hook.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings November 10, 2026 06:30
@richlundeen
Richard Lundeen (richlundeen) marked this pull request as draft November 10, 2026 06:38

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Unresolved issues can leave draft submissions stuck after a failed start, prevent generation data from refreshing when runtime availability changes, and block regeneration for maximum-length dataset names.

3 open issues
What changed in this PR

This PR connects CoPyRIT’s dataset catalog to prompt generation, allowing users to create policy-based datasets, review generated policy details, and launch scenarios with those datasets selected.

Changes:

  • Adds generation navigation, reusable generator views, preflight checks, and dataset regeneration links.
  • Bundles ASSERT behavior and suite presets, with supporting generation, scoring, tracing, and analytics interfaces.
  • Adds frontend coverage, isolated browser-test configuration, CI wiring, and user documentation.
File Description
THIRD_PARTY_NOTICES.txt Updates ASSERT redistribution attribution.
tests/​unit/​executor/​promptgen/​test_target_objective_generator.py Tests generation estimates and validation.
tests/​unit/​common/​test_lazy_package_imports.py Updates analytics export expectations.
tests/​unit/​backend/​test_prompt_generation_fixture.py Checks offline generator responses.
tests/​unit/​assert_mocks.py Adds checkpoint and generated-group fixtures.
pyrit/​score/​true_false/​true_false_fallback_scorer.py Exposes configurable fallback triggers.
pyrit/​score/​scorer.py Identifies missing-evidence results.
pyrit/​score/​observation/​__init__.py Exports execution-trace observation helpers.
pyrit/​score/​float_scale/​float_scale_fallback_scorer.py Exposes configurable fallback triggers.
pyrit/​scenario/​core/​scenario.py Extracts scenario identity parameter handling.
pyrit/​prompt_target/​common/​target_trace_config.py Attaches conversation identifiers to spans.
pyrit/​prompt_target/​common/​prompt_target.py Exposes target tracing configuration.
pyrit/​models/​score/​__init__.py Exports execution-trace models.
pyrit/​models/​analytics.py Adds binary and macro rate models.
pyrit/​executor/​promptgen/​target_objective_generator.py Adds call and token estimates.
pyrit/​executor/​promptgen/​__init__.py Exports objective generation results.
pyrit/​datasets/​seed_datasets/​generated/​target_objective_provider.py Extracts reusable result packaging.
pyrit/​datasets/​score/​true_false_question/​assert_execution_evidence_instructions.yaml Defines trace-evidence judging instructions.
pyrit/​datasets/​score/​assert/​judge_presets/​tool-use.yaml Adds tool-use judging dimensions.
pyrit/​datasets/​score/​assert/​judge_presets/​safety-extended.yaml Adds harm and privacy dimensions.
pyrit/​datasets/​score/​assert/​judge_presets/​safety-core.yaml References core safety dimensions.
pyrit/​datasets/​score/​assert/​judge_presets/​robustness.yaml Adds robustness judging dimensions.
pyrit/​datasets/​score/​assert/​judge_presets/​policy-adherence.yaml Adds policy-adherence judging.
pyrit/​datasets/​score/​assert/​judge_presets/​operational.yaml Adds workflow and escalation judging.
pyrit/​datasets/​score/​assert/​judge_presets/​multi-turn.yaml Adds conversation continuity judging.
pyrit/​datasets/​score/​assert/​judge_presets/​instruction-following.yaml Adds instruction-following judging.
pyrit/​datasets/​score/​assert/​judge_presets/​grounding.yaml Adds grounding and attribution judging.
pyrit/​datasets/​score/​assert/​judge_presets/​communication.yaml Adds communication-quality judging.
pyrit/​datasets/​score/​assert/​judge_presets/​alignment.yaml Adds honesty and verification judging.
pyrit/​datasets/​score/​assert/​dimension_system_prompt.yaml Adds custom-dimension judge template.
pyrit/​datasets/​assert_suites/​travel_planner.yaml Bundles travel-planner suite.
pyrit/​datasets/​assert_suites/​travel_planner_benchmark.yaml Bundles quality-only travel suite.
pyrit/​datasets/​assert_suites/​telecom_customer_service.yaml Bundles telecom support suite.
pyrit/​datasets/​assert_behaviors/​unsupported_conclusion_failures.yaml Bundles unsupported-conclusion behavior.
pyrit/​datasets/​assert_behaviors/​unit_conversion_failures.yaml Bundles unit-conversion behavior.
pyrit/​datasets/​assert_behaviors/​underused_context_failures.yaml Bundles context-underuse behavior.
pyrit/​datasets/​assert_behaviors/​unauthorized_action_failures.yaml Bundles unauthorized-action behavior.
pyrit/​datasets/​assert_behaviors/​tool_parameter_formatting_failures.yaml Bundles tool-argument behavior.
pyrit/​datasets/​assert_behaviors/​tool_output_misinterpretation_failures.yaml Bundles tool-output interpretation behavior.
pyrit/​datasets/​assert_behaviors/​tool_orchestration_errors.yaml Bundles tool-orchestration behavior.
pyrit/​datasets/​assert_behaviors/​tool_call_turn_protocol_failures.yaml Bundles tool-turn protocol behavior.
pyrit/​datasets/​assert_behaviors/​tool_call_error_recovery_failures.yaml Bundles tool-error recovery behavior.
pyrit/​datasets/​assert_behaviors/​tabs_vs_spaces.yaml Bundles indentation preference-bias behavior.
pyrit/​datasets/​assert_behaviors/​sycophancy.yaml Bundles sycophancy behavior.
pyrit/​datasets/​assert_behaviors/​suicide_self_harm.yaml Bundles self-harm safety behavior.
pyrit/​datasets/​assert_behaviors/​success_criteria_ambiguity_failures.yaml Bundles success-criteria ambiguity behavior.
pyrit/​datasets/​assert_behaviors/​stereotyping.yaml Bundles stereotyping behavior.
pyrit/​datasets/​assert_behaviors/​stale_state_failures.yaml Bundles stale-state behavior.
pyrit/​datasets/​assert_behaviors/​shimano_vs_sram.yaml Bundles cycling-brand preference behavior.
pyrit/​datasets/​assert_behaviors/​response_completeness_failures.yaml Bundles response-completeness behavior.
pyrit/​datasets/​assert_behaviors/​repeated_action_loop_failures.yaml Bundles repeated-action behavior.
pyrit/​datasets/​assert_behaviors/​prompt_injection.yaml Bundles prompt-injection behavior.
pyrit/​datasets/​assert_behaviors/​procedure_adherence_failures.yaml Bundles procedure-adherence behavior.
pyrit/​datasets/​assert_behaviors/​premature_termination_failures.yaml Bundles premature-termination behavior.
pyrit/​datasets/​assert_behaviors/​poor_retrieval_failures.yaml Bundles retrieval-quality behavior.
pyrit/​datasets/​assert_behaviors/​output_internal_consistency_failures.yaml Bundles output-consistency behavior.
pyrit/​datasets/​assert_behaviors/​out_of_scope_request_failures.yaml Bundles scope-boundary behavior.
pyrit/​datasets/​assert_behaviors/​observation_neglect_failures.yaml Bundles observation-neglect behavior.
pyrit/​datasets/​assert_behaviors/​ios_vs_android.yaml Bundles mobile-platform preference behavior.
pyrit/​datasets/​assert_behaviors/​inter_agent_handoff_failures.yaml Bundles agent-handoff behavior.
pyrit/​datasets/​assert_behaviors/​intent_misinterpretation_failures.yaml Bundles intent-interpretation behavior.
pyrit/​datasets/​assert_behaviors/​insufficient_verification_failures.yaml Bundles insufficient-verification behavior.
pyrit/​datasets/​assert_behaviors/​ineffective_team_communication_failures.yaml Bundles agent-communication behavior.
pyrit/​datasets/​assert_behaviors/​incorrect_tool_selection_failures.yaml Bundles tool-selection behavior.
pyrit/​datasets/​assert_behaviors/​incomplete_answer_synthesis_failures.yaml Bundles answer-synthesis behavior.
pyrit/​datasets/​assert_behaviors/​identity_verification_failures.yaml Bundles identity-verification behavior.
pyrit/​datasets/​assert_behaviors/​harmful_medical_advice.yaml Bundles medical-safety behavior.
pyrit/​datasets/​assert_behaviors/​grounding_attribution_errors.yaml Bundles grounding-error behavior.
pyrit/​datasets/​assert_behaviors/​goal_drift_failures.yaml Bundles goal-drift behavior.
pyrit/​datasets/​assert_behaviors/​flawed_action_plan_failures.yaml Bundles planning-failure behavior.
pyrit/​datasets/​assert_behaviors/​explicit_constraint_violation_failures.yaml Bundles constraint-violation behavior.
pyrit/​datasets/​assert_behaviors/​escalation_judgment_failures.yaml Bundles escalation-decision behavior.
pyrit/​datasets/​assert_behaviors/​doxxing.yaml Bundles private-information protection behavior.
pyrit/​datasets/​assert_behaviors/​crystal_mountain_vs_snoqualmie.yaml Bundles resort preference-bias behavior.
pyrit/​datasets/​assert_behaviors/​conversation_coherence_breakdown.yaml Bundles conversation-coherence behavior.
pyrit/​datasets/​assert_behaviors/​constraint_propagation_failures.yaml Bundles cross-agent constraint behavior.
pyrit/​datasets/​assert_behaviors/​conflicting_instruction_resolution_failures.yaml Bundles instruction-conflict behavior.
pyrit/​datasets/​assert_behaviors/​actionability_failures.yaml Bundles answer-actionability behavior.
pyrit/​datasets/​__init__.py Exports ASSERT preset accessors.
pyrit/​common/​path.py Defines bundled preset locations.
pyrit/​backend/​services/​service_lifecycle.py Resets generation service during cleanup.
pyrit/​backend/​services/​runtime_lifecycle.py Includes generation work in runtime lifecycle.
pyrit/​backend/​main.py Registers prompt-generation routes.
pyrit/​analytics/​__init__.py Exports ASSERT metrics and rate helpers.
frontend/​src/​utils/​routeParams.ts Adds dataset-preselected launch URLs.
frontend/​src/​utils/​routeParams.test.ts Tests dataset URL encoding and parsing.
frontend/​src/​test-utils/​replaceText.ts Adds efficient text replacement helper.
frontend/​src/​hooks/​useRequestedDatasets.ts Validates requested dataset selections.
frontend/​src/​hooks/​usePromptGenerators.ts Loads runtime-specific generator catalog.
frontend/​src/​hooks/​usePromptGenerationPreflight.ts Debounces validation and estimate requests.
frontend/​src/​hooks/​usePromptGeneration.ts Loads and polls generation records.
frontend/​src/​hooks/​useAssertPolicyMetrics.ts Loads completed-run ASSERT metrics.
frontend/​src/​hooks/​useAssertPolicyMetrics.test.tsx Tests metrics loading and retry behavior.
frontend/​src/​hooks/​useAssertLibrary.ts Loads bundled behavior and suite templates.
frontend/​src/​components/​Scenarios/​ScenarioRunPage.tsx Displays completed ASSERT run metrics.
frontend/​src/​components/​Scenarios/​ScenarioRunPage.test.tsx Tests conditional metrics display.
frontend/​src/​components/​Scenarios/​scenarioLaunchForm.ts Seeds dataset selections from links.
frontend/​src/​components/​Scenarios/​assertPolicyRun.ts Identifies ASSERT policy runs.
frontend/​src/​components/​Scenarios/​AssertPolicyMetricsPanel.styles.ts Styles metrics presentation.
frontend/​src/​components/​PromptGeneration/​TargetObjectiveSummary.tsx Displays generated objective counts.
frontend/​src/​components/​PromptGeneration/​RegenerateDatasetLink.tsx Links generated datasets to regeneration.
frontend/​src/​components/​PromptGeneration/​RegenerateDatasetLink.test.tsx Tests regeneration link availability.
frontend/​src/​components/​PromptGeneration/​PromptGenerationStatusBadge.tsx Displays generation status badges.
frontend/​src/​components/​PromptGeneration/​promptGenerationRoutes.ts Defines generation routes and query parameters.
frontend/​src/​components/​PromptGeneration/​promptGenerationRoutes.test.ts Tests generation route helpers.
frontend/​src/​components/​PromptGeneration/​GenericReviewStep.tsx Provides a generic review continuation view.
frontend/​src/​components/​PromptGeneration/​GenericGenerationSummary.tsx Displays generic scalar result summaries.
frontend/​src/​components/​PromptGeneration/​generatorUi.ts Defines generator UI extension interfaces.
frontend/​src/​components/​PromptGeneration/​generatorRegistry.tsx Selects specialized or generic generator views.
frontend/​src/​components/​PromptGeneration/​GenerationTargetFields.test.tsx Tests target selection and errors.
frontend/​src/​components/​PromptGeneration/​GenerationSummaryFacts.tsx Renders reusable result facts.
frontend/​src/​components/​PromptGeneration/​generationFormHelpers.test.ts Tests form validation helpers.
frontend/​src/​components/​PromptGeneration/​GenerateDatasetLinks.tsx Links scenarios to matching generators.
frontend/​src/​components/​Datasets/​DatasetSelection.tsx Adds dataset regeneration entry point.
frontend/​src/​components/​Datasets/​DatasetSelection.test.tsx Tests dataset regeneration integration.
frontend/​src/​components/​Datasets/​DatasetCatalog.tsx Adds generation navigation button.
frontend/​src/​components/​Datasets/​DatasetCatalog.test.tsx Tests generation navigation.
frontend/​src/​App.tsx Registers generation pages.
frontend/​README.md Documents isolated browser checks.
frontend/​playwright.prompt-generation.config.ts Configures offline generation browser tests.
frontend/​playwright.config.ts Excludes the dedicated generation spec.
frontend/​package.json Adds generation browser-test command.
doc/​myst.yml Adds trace-scoring documentation navigation.
doc/​gui/​0_gui.md Documents GUI dataset generation.
doc/​code/​scoring/​1_true_false_scorers.py Documents custom ASSERT judging.
doc/​code/​scoring/​1_true_false_scorers.ipynb Mirrors custom judging documentation.
doc/​code/​scoring/​0_scoring.py Links execution-trace scoring guidance.
doc/​code/​scoring/​0_scoring.ipynb Mirrors trace-scoring guidance link.
doc/​code/​executor/​7_promptgen.py Demonstrates checkpoint review and continuation.
doc/​code/​analytics/​0_attack_results.md Documents rates and ASSERT policy metrics.
.github/​workflows/​frontend_tests.yml Adds isolated generation browser-test CI job.

Review effort: Balanced

Comment thread frontend/src/hooks/usePolledRecord.ts Resolved
…converters

- Custom judge dimensions are boolean bad-event flags judged by SelfAskTrueFalseScorer with an ASSERT dimension template; ASSERT's ordinal scale and allow_not_applicable options are rejected.
- Repeated samples use TrueFalseCompositeScorer over the repeated judge with an ASSERT vote (ties count as failures, undetermined samples excluded, category re-vote with override warning), replacing the bespoke sampled scorers.
- Public exports trimmed to AssertJudgeDimension, AssertJudgePreset, AssertSampleMetadata, and the preset list/load functions.
- foundry.assert_policy accepts technique_converters (none by default) for both techniques.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- AssertTechnique is removed. The technique class is built from the AttackTechniqueRegistry, with red_teaming as the default (ASSERT's scenario case).
- The baseline, now on by default, sends each group's stored system and user prompts (ASSERT's prompt case).
- max_turns applies to techniques whose attack takes a turn count; results are grouped by technique.
- AssertPolicy.VERSION is 2, so runs from version 1 do not resume.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- allow_not_applicable: a not-applicable answer is undetermined with assert_not_applicable metadata; repeated samples exclude it and keep the marker only when every sample is not applicable.
- ASSERT's ordinal scale is accepted with a PyRIT violation_at grade. The judge's grade position is thresholded by FloatScaleThresholdScorer, so every dimension still yields a true/false verdict, and the grade is kept in assert_grade metadata. Graded dimensions can be the objective.
- AssertDimensionMetadata is exported from pyrit.score. Default identities are unchanged.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

@romanlutz Roman Lutz (romanlutz) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed as the incremental diff vs richlundeen-assert-generation-backend (PR #4134), ~9k added lines. Overall this is high-quality frontend work: the TS types mirror the backend pydantic models exactly, the API client matches every route, validation replicates the backend validators, and the e2e setup (real FastAPI app over an offline target, plus a contract-pinning unit test) is notably better than a hand-rolled fake. Inline comments cover the bugs; a few broader notes:

Design

  • The three generator forms triplicate an identical ~40-line shell (state, submit, preflight, footer plumbing); a shared hook would keep the preflight request shape in one place.
  • AssertGenerationFormContent is ~530 lines with 15 useStates; the suite section (4 parallel states + table) wants to be its own component.
  • Polling stops on awaiting_review, so a 'Review needed' page/list never refreshes if the review is continued elsewhere; Continue then 409s with no reload path.
  • Web-search capability is handled asymmetrically: the research-role filter requires supports_web_search === true (targets without capabilities are hidden), while the generation-target fallback only rejects === false.

Test gaps

  • The preflight transport-failure path (warning + still-enabled Generate + estimate card state) has zero coverage.
  • Suite-mode validation (duplicate dataset names, 100-dataset cap, label length, cleared name) is untested.
  • usePolledRecord's subtlest branches are untested: 404 arriving mid-poll, unmount mid-fetch, a changing recordKey.
  • assertDraftFromRequest is never tested with a stored stratified request.
  • The e2e journey never exercises cancel/retry/delete/draft/group against the real backend; given the fixture serves the real routes, a short cancel-then-retry journey would be cheap insurance.

Comment thread frontend/src/hooks/usePolledRecord.ts Resolved
Comment thread doc/gui/0_gui.md Resolved
Comment thread frontend/e2e/prompt-generation.spec.ts Resolved
@richlundeen
Richard Lundeen (richlundeen) force-pushed the richlundeen-assert-gui-generation-plan branch from 6feb697 to b3c7848 Compare November 10, 2026 09:58
@richlundeen
Richard Lundeen (richlundeen) force-pushed the richlundeen-assert-gui-generation-plan branch 2 times, most recently from 6cd2cf7 to d50c7d0 Compare November 10, 2026 19:38
Adds a scenario-local assert_package technique to foundry.assert_policy: PyRIT's RedTeamingAttack whose tester uses ASSERT's own tester system prompt (pinned 04b713fe) filled with each group's stored tester instructions. It is the default technique alongside the baseline; red_teaming stays selectable. Groups without tester instructions are skipped or rejected per incompatible_technique_policy.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Resolve judge presets in a worker thread instead of the synchronous validator. Drop a judge sample whose judgment stays invalid after retries (scoring fails only when every sample does), as ASSERT does. Require native multi-turn targets for turn-taking techniques in foundry.assert_policy, keep turn settings a registered technique sets itself, pass the adversarial chat only to techniques that use one, and warn once per even sample count.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@richlundeen
Richard Lundeen (richlundeen) force-pushed the richlundeen-assert-gui-generation-plan branch from d50c7d0 to 9f523be Compare November 10, 2026 23:18

@romanlutz Roman Lutz (romanlutz) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-review of d50c7d0 (incremental vs the rebased #4134 head). The rework addressed two of my earlier bugs by removing their feature surface: drafts (and the PATCH/start two-step with its stale expected_version) are gone, and server-side groups (and the divergent group-status aggregation) were replaced by a batch create with list-page grouping — both simplifications look clean, and the hard-coded supported-generator registry with an explicit "unsupported generator" notice is a reasonable trade. The other earlier comments (default target dropped on deep links, estimate card stuck on "Calculating..." after a preflight failure, suite dataset names not following label edits, 128-char regenerate no-op, usePolledRecord remount contract, dataset:named: duplication, "Pause to review" doc wording, the "21 permissible" e2e assertion) still apply at this head.

Add AssertDimensionResult, AssertCategoryJudgment (with AssertNodeJudgment) and AssertSampleVotes in pyrit.models as the only readers and writers of the ASSERT score metadata keys, keeping the stored key format. Missing keys are unset and malformed present data raises ValueError. The scenario judge wrapper now records the assert_dimension marker on judged and skipped scores. The custom-dimension judge renders its request from a YAML SeedPrompt, and both ASSERT response handlers validate and convert the decoded response through a new JsonSchemaResponseHandler._convert_response hook instead of parsing twice. AssertDimensionMetadata and AssertSampleMetadata are removed.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ence

ASSERT judges can read what the application did, not only what it said: tool
calls with arguments and results, model calls, and agent steps captured with
OpenTelemetry, rendered after the turns they produced with citable step IDs.

- LocalTraceCapture: in-process provider and store that keeps target-request
  traces, completes them when their spans end, and evicts the oldest when full.
- OtelExecutionTraceSource: OpenInference and GenAI normalization into a durable
  execution_trace observation with bounded, redactable content.
- ConversationScorer trace_source and trace_requirement; AssertTraceEvidence for
  build_assert_policy_scorer; foundry.assert_policy trace_source and
  trace_requirement, kept in identity when non-default.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Withdraw completion when a span starts after it; export and completion share the capture lock; evict any trace when full with explicit loss markers and bounded bookkeeping; render steps in parent cycles; remove the unreachable unattributed block; require a trace source for trace_requirement; document strict snapshot matching and citation behavior.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…mplate

additional_instructions is an explicit dimension_system_prompt.yaml parameter rendered in the sandbox instead of appended after rendering; the prompt is unchanged when it is empty.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…only parameters

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…layer

Bring the published layer-3 metrics (4848f91) onto the rebuilt layer 2 (06ccdf2). The merge applied
without conflicts. The Foundry notebook keeps layer 2's outputs and is synced from foundry.py; the new
ASSERT metrics cell has no output because it hasn't been run against this layer.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…distinct

ASSERT metrics now let a saved registry name decide whether foundry.assert_policy produced a result,
so another scanner's AssertPolicy class isn't mistaken for ASSERT. Older results without a registry
name must come from PyRIT's AssertPolicy module. The metrics route answers other scenarios with a
400 problem of type /errors/not-assert-policy-run. The run page mounts the panel on a matching
registry name, or tentatively on the class name for older runs, and hides it only for that problem
type; compatibility, validation and other errors still show. A supplied objective scorer's
uncategorized verdicts are reported as the objective dimension, not as ASSERT's policy judge.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…sions

A result's policy now comes only from the stored seed group with exactly the seeds it recorded, and
only when that group's taxonomy matches the taxonomy the policy judge recorded in its saved scorer
identifier, which survives sampling and trace wrappers. A replaced or edited dataset leaves the
conversation without a matching stored policy instead of reporting another group's categories.
Unmarked legacy scores count as ASSERT dimensions only with that judge provenance, so a supplied
scorer that uses the policy_violation category is reported as the objective dimension. Category
rates are kept per policy, with a policy_id, so policies that share a behavior or category name
aren't pooled, and the panel names them apart. Results without a scenario module are no longer
accepted as AssertPolicy by class name alone.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
A stored seed group's policy is used only when the policy score's saved identifier comes from the
scenario's built-in judge wrapper and records the same taxonomy; a policy score without that evidence
leaves the conversation without a matching stored policy, while its dimension rates still count it.
Only questions under that wrapper count as judge evidence, so a supplied SelfAskTrueFalseScorer whose
question carries ASSERT-shaped metadata and the policy_violation category is reported as the objective
dimension. Category rates are keyed by the judged policy (taxonomy, application context and target
instructions), so policies that share a taxonomy but differ in context or instructions aren't pooled.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The metrics no longer read a stored group's assigned category. ASSERT's judges recompute
policy_violation from their category judgments, so every violation verdict already names a violated
category; ASSERT's attribution of category-less violations to the generated category isn't needed and
would depend on seed metadata that can be edited after a run. A stored policy verdict that disagrees
with its category judgments is now rejected as malformed instead of being attributed, and
AssertCategoryMetrics drops attributed_by_fallback.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrates -3 d0b7c2a (typed judgments, provenance and verdict corrections) under the published -4 head; no conflicts.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrates -4 1c0add0 (rebuilt -3 d0b7c2a) under the published -5 head; no conflicts.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrates -5 22c7a75 (rebuilt -3 d0b7c2a) under the published -6 head; no conflicts.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Replaces the per-generator links on scanner launch pages with one Browse datasets / Generate datasets group in the Datasets header. Generate waits for the current runtime's generators, then opens the scenario's only follow-up generator (ASSERT for foundry.assert_policy), otherwise the generator chooser.

Linked ?dataset= names stay explicit, exact selections for the server to validate instead of being checked against a second catalog fetch; only identical names are deduplicated. A blank name, or any name on a scanner that takes no datasets, blocks the estimate and launch with an error and a link that removes them. Regenerate links read the stored request by the dataset's exact selection key.

foundry.assert_policy marks its datasets as required and asks for one at launch, using the rebuilt -3's ASSERT scenario check. Scenario.get_dataset_options reports inline seeds as fixed sources, so inline-only scenarios offer no dataset picker while their limits and filters stay editable.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The rebuilt -3 launch-request tests build foundry.assert_policy requests without a dataset, which this layer now rejects with 'Select an ASSERT dataset.' They select one so they keep checking the default-scoring rules.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Merged against the -5 head this layer last merged (22c7a75), so main's
squashed lower layers replace the old ones. Main dropped the GUI's ASSERT
default-scoring guard, so this layer keeps only its own linked-dataset
check and names the ASSERT dataset requirement requiresDatasetSelection.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Drop the objective summary the merged backend never returns, which failed the
  prompt-generation E2E journey.
- Let scenarios declare a minimum dataset selection (ScenarioDatasetOptions.min_selected,
  set by foundry.assert_policy) instead of checking the scenario name, and report a missing
  dataset on the picker, moving focus there on launch.
- Reload a generation when review actions find it moved on (409), show estimate and
  generator-list errors with retries, and add Check again to stale progress.
- Remove client copies of library validation (repeated terms, web-search target rules,
  unregistered targets) so preflight reports them.
- Keep multi-line review examples unless edited, reuse a reviewed taxonomy when
  regenerating, and move review and from-dataset fetching into hooks.
- Smaller fixes: remove the unused 'saving' status, keep long suite names distinct, fit
  suite name inputs, one 'Edit & regenerate' and 'Generate datasets' label, hide Reset and
  Generate where they do nothing, and let the server reject blank linked dataset names.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Rename the remaining "Datasets > Generate dataset" doc references to "Generate datasets"
  in the prompt generation and Foundry scanner docs, keeping each notebook pair in sync.
- Inline seeds no longer report a required dataset selection, and ScenarioDatasetOptions
  rejects a min_selected above max_selected.
- Type the reused review taxonomy as AssertTaxonomy, parsed with the review editor's reader.
- Assert the server's error for a blank linked dataset, and drop a doubled blank line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Generate a new taxonomy when the application context or suggested category count
  changes, not only the behavior or policy text.
- Focus the missing-dataset picker without scrolling the app shell.
- Show the server's field messages with a 422 in the scan estimate and launch errors, so a
  blank linked dataset name says what failed.
- Offer Generate datasets only on scanners that accept any dataset name.
- Use one wording for a required dataset selection in the library, foundry.assert_policy,
  and the GUI.
- Reload the generation when loading its review finds it moved on, and pin the Save-path
  409 reload.
- Show Reset datasets only when sources or per-dataset limits are edited.
- List a preflight error every suite dataset shares once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The review editor reloads the generation when loading the review returns 409. Extend the
retry test to fail the load with a 500 and assert neither the failure nor Retry reloads the
generation, so widening the condition is caught.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@richlundeen

Copy link
Copy Markdown
Contributor Author

review:5839082233

Thanks. Addressed in c4694df and 90c1605:

  • Polling stops on awaiting_review: the review view now gets an onReload from the page. When loading the review, Save or Continue gets a 409 (the review was continued or cancelled elsewhere), the page re-reads the generation, so the badge and form update instead of 409ing on every click. Other failures still just offer Retry. The list page still refreshes on open rather than polling review rows.
  • Web-search asymmetry: the client web-search rules are gone. The research picker no longer filters by supports_web_search, and the generation-target fallback check is removed; preflight's validate_targets reports the problem once, so both roles follow the library's rule.
  • Test gaps: added a 404-mid-poll test (polling stops, and the stale warning now has Check again), suite-mode tests for the cleared label and duplicate dataset names, stratified and no-replacement random round trips through assertDraftFromRequest, and an assertion that Generate stays enabled after a failed check. The cancel/retry e2e journey isn't added: the offline job finishes in about a second, so cancelling it would race; unit tests cover cancel and retry.

Verified on published commit b196615c356dee1a8c7874953496dde668d34b46.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review completed. No blocking concerns remain. This review records source coverage; merging is handled separately.

@romanlutz Roman Lutz (romanlutz) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-review at 8f878a5 (incremental vs the rebuilt #4134 head, verified ancestor). Every earlier inline comment is genuinely fixed in code, matching the replies: the new useGenerationTargetSelection derives the default until the user chooses (late registry handled, research role included), nextDatasetName shortens the base before the suffix, the preflight error state gets "Check again" plus an explicit no-estimate message (with form-level regressions), usePolledRecord scopes state by record key + runtime generation and gates on readiness, suite dataset names follow the label, RegenerateDatasetLink shares the selection-key helper and treats only 404 as not-generator-made, and the doc/e2e nits are fixed. The new scanner work (grouped dataset actions, exact linked names, backend inline-seeds guard) is careful and well-tested — exact-name semantics hold end to end and the deleted useRequestedDatasets responsibilities are all accounted for. Two small open points from before: the review editor's last-write-wins concurrency note (no reply), and the web-search capability asymmetry (research filter requires supports_web_search === true while the generation-fallback check only rejects === false). New comments below are edge-case UX dead-ends around hand-edited ?dataset= links.

const adversarialTargets = targets.filter(
(target: TargetInstance) => target.capabilities?.supports_multi_turn === true,
)
const [linkedNames] = useState(() => [...linkedDatasetNames])

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

linkedNames is frozen at mount, so linkedDatasetError never clears when the user fixes the selection in the form: open a launch link with a blank ?dataset= name, add a valid dataset via the picker — launch stays blocked, and the "open without the blank names" escape remounts the form and discards the manual edits. Deriving the error from the current selection (or clearing it once the linked names are no longer in sources) would avoid the dead end. Edge case — only reachable from a hand-edited URL.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

inline:4605433059

Addressed. The blank-name check that was computed once at mount is gone: blank or unknown linked names go to the server, and fixing the selection in the picker clears the estimate error. The only error still decided at mount is for a scenario that can't take linked datasets at all, which no form edit could fix, so Open without the linked datasets is the right way out there. This code now comes from #4476 (-5.5) on main, merged into this PR in 2342519.

Verified on published commit 2342519e99f16721541bc87c45b1c364331fe9a2.

const [emptySelections, setEmptySelections] = useState<string[]>([])
const selected: ScenarioDatasetSourceInput[] = request.sources ?? defaults.sources.map((source) => ({ name: source.name }))
const canSelect = options.supports_overrides && options.mode !== 'fixed' && selected.length > 0
const canSelect = options.supports_overrides && options.mode !== 'fixed'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linked ?dataset= names can now wedge a fixed-mode scenario: the link injects the name into sources, but canSelect is false for fixed mode so the picker/Reset/Remove stay hidden, and only subset mode gets a client-side invalid-source error below — the user sees just the server's "Dataset sources are fixed" estimate error and can recover only by editing the URL. A fixed-mode validation branch (or the same escape link the unsupported case gets) would close that. Relatedly, no test covers a linked name against a fixed- or subset-mode scenario.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

inline:4605433067

Fixed through #4476 (-5.5), which this PR merged from main in 2342519. A scenario with fixed sources now can't take linked ?dataset= names: the launch is blocked with "This scenario can't take the linked datasets: …" and an Open without the linked datasets link, so nothing is injected into sources the picker can't edit. ScenarioDetail.test.tsx covers a linked name against fixed sources. This linked-dataset code now lives on main; this PR no longer changes it.

Verified on published commit 2342519e99f16721541bc87c45b1c364331fe9a2.

@richlundeen
Richard Lundeen (richlundeen) marked this pull request as ready for review November 21, 2026 00:57
Merge main 830f745, which includes microsoft#4476 (-5.5), against a virtual base of
3e0820b plus microsoft#4476's initial carve (60be4e9), so main's reviewed scanner and
dataset behavior wins and this branch keeps only its generation additions.

- DatasetActions: main's new-tab Browse datasets plus this branch's Generate
  datasets, now in its own component so callers without a scenario (the preset
  editor main added) show Browse only and don't load generators.
- DatasetCatalog: keep main's shared origin labels and this branch's Generate
  datasets header button.
- ScenarioDetail tests: keep main's new tests; the Datasets header test checks
  both the new-tab Browse link and the Generate link.
- Docs: keep main's Scanner dataset paragraph and Origins sentence; add the
  Generate datasets section.
- prompt-generation e2e: follow main's origin labels ("Generated") and its empty
  selection, which shows only the picker.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@richlundeen

Copy link
Copy Markdown
Contributor Author

review:5946159233

Thanks for the re-review. Status at 2342519, which merges main with #4476 (-5.5), where this PR's scanner and dataset selection changes now live:

  • Linked ?dataset= dead ends: both are handled by FEAT: Scanner dataset selection: required, linked and first datasets (-5.5) #4476's code (replied on each thread).
  • Review concurrency: intentional and stated in the description's Known limitations; replied on that thread.
  • Web-search asymmetry: gone since c4694df. The GUI no longer filters or checks targets by supports_web_search; the server preflight reports a target that lacks web-search support once, under the library's rule.

Verified on published commit 2342519e99f16721541bc87c45b1c364331fe9a2.

The preset editor's Datasets header now shows Generate datasets under the
launch page's rule: only for a scenario that takes datasets and accepts any
dataset name, for the preset's scenario, and unavailable until the runtime's
generator list loads. Both pages share acceptsAnyNamedDataset. The GUI doc now
says Generate appears only for scanners that accept any named dataset.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@romanlutz Roman Lutz (romanlutz) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed across four rounds (stacked increments, then the post-carve-out diff vs main). All earlier findings are fixed, documented as known limitations, or restructured away; the final repair pass and preset-editor addition check out with regressions, and CI is green. Approving.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants